-
Notifications
You must be signed in to change notification settings - Fork 3.3k
ES clear: delete indices themselves, not all the docs #15449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
✅ Meticulous spotted 0 visual differences across 992 screens tested: view results. Meticulous evaluated ~8 hours of user flows against your PR. Expected differences? Click here. Last updated for commit ada6fcd. This comment will update as new commits are pushed. |
Codecov Report❌ Patch coverage is ❌ Your patch status has failed because the patch coverage (65.60%) is below the target coverage (75.00%). You can increase the patch coverage or adjust the target coverage. 📢 Thoughts on this report? Let us know! |
Bundle ReportBundle size has no change ✅ |
…m:datahub-project/datahub into PFP-2064/esclear-is-extremely-inefficient
we were using delete_by_query with a match_all query to delete docs. This can be very ineffiicient in large indices. Instead is it much faster to delete the index and create it again